Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@test/functional/test_framework/test_node.py`:
- Line 723: The peer matching assumes addrbind is always present and can raise
KeyError; update the filter in test_node.py where getpeerinfo() is iterated (the
list comprehension that builds info) to safely handle missing addrbind by using
peer.get("addrbind") (or "in" check) when comparing to dst_addr_and_port, so
replace peer["addrbind"] == dst_addr_and_port with a safe check such as
peer.get("addrbind") == dst_addr_and_port to avoid KeyError for peers without
addrbind while still matching addr and addrbind correctly for our_addr_and_port
and dst_addr_and_port.

---

Nitpick comments:
In `@src/rpc/node.cpp`:
- Around line 7-11: Move the config include so it appears before any other
headers: place `#if` defined(HAVE_CONFIG_H) / `#include` <config/bitcoin-config.h>
at the top of src/rpc/node.cpp (above `#include` <addressindex.h>) so macros like
HAVE_MALLOC_INFO are defined before other headers are processed; update the
include block around the existing preprocessor directives accordingly to ensure
config is included first.

These findings are from an automated code review. Verify each finding against the current code and only fix it if needed.

In `src/util/system.cpp`:
- [SUGGESTION] lines 1-7: Missing direct config include for src/util/system.cpp
  Upstream `bitcoin#29404` adds a direct `#include <config/bitcoin-config.h>` to `src/common/system.cpp` (renamed from `src/util/system.cpp` in `bitcoin#28076`). Dash still has the file at its original path and the backport does not add the config include. The file uses config symbols (`HAVE_MALLOPT_ARENA_MAX`, `HAVE_FDATASYNC`, etc.) but receives them transitively via `util/system.h`. Not blocking — matches upstream intent to eventually remove transitive config includes from headers.

These findings are from an automated code review. Verify each finding against the current code and only fix it if needed.

In `src/util/system.cpp`:
- [SUGGESTION] lines 1-7: Missing direct config include for src/util/system.cpp (bitcoin#29404 prereq)
  Upstream bitcoin#29404 adds a direct `#include <config/bitcoin-config.h>` to `src/common/system.cpp`, the file that upstream bitcoin#28076 renamed from `src/util/system.cpp`. Because Dash has not backported #28076, the file still lives at `src/util/system.cpp` and the scripted-diff did not target it. Verified: line 7 begins with `#include <util/system.h>` and no direct config include is present, while the file consumes config macros later (`HAVE_MALLOPT_ARENA_MAX` at lines 60/1418, `HAVE_FDATASYNC` at line 1233). Non-blocking: the macros are still supplied transitively via `util/system.h`, so behavior is unchanged. The full alignment requires backporting bitcoin#28076 first; a partial fix is to add the direct include manually here to match #29404's intent of making config dependencies explicit.

These findings are from an automated code review. Verify each finding against the current code and only fix it if needed.

In `src/util/system.cpp`:
- [SUGGESTION] src/util/system.cpp:5-9: Carried-forward (STILL VALID): missing direct bitcoin-config.h include in src/util/system.cpp
  Verified at 19b26e41: src/util/system.cpp still goes straight from the license header to `#include <util/system.h>` with no direct `#include <config/bitcoin-config.h>`, even though the file uses HAVE_MALLOPT_ARENA_MAX (lines 60, 1418), HAVE_FDATASYNC (line 1233), HAVE_POSIX_FALLOCATE (line 1319), and HAVE_SYSTEM (line 1364). Upstream bitcoin#29404's scripted-diff added the direct include to the same translation unit, but upstream's file path is src/common/system.cpp after bitcoin#28076's rename, which Dash hasn't backported — so the scripted-diff invocation in this PR missed Dash's still-unrenamed src/util/system.cpp.

  This builds today only because src/util/system.h:14-16 still pulls in `<config/bitcoin-config.h>` transitively. That transitive guarantee is exactly what #29404 is preparing to remove; once a future backport drops the include from headers, this file will silently lose its HAVE_* definitions and fall through to the disabled #else branches (no fdatasync, no posix_fallocate, no mallopt tuning). To honor the upstream invariant for the Dash file layout, add the standard guarded include here.
- [BLOCKING] src/util/system.cpp:1-25: Carried-forward: src/util/system.cpp missing direct config include (bitcoin#29404 soft prereq via unbackported bitcoin#28076)
  STATUS: STILL VALID (prior finding from ae9e403d revalidated against current head 19b26e41).

  Upstream bitcoin#29404's scripted-diff added a direct `#include <config/bitcoin-config.h>` to every .cpp/.h that references a HAVE_* token from bitcoin-config.h.in. The equivalent file in upstream is `src/common/system.cpp` — renamed from `src/util/system.cpp` by bitcoin#28076, which Dash has not backported. Because Dash still has the file at the old path, the scripted-diff invocation in this PR did not reach it.

  Evidence at current head:
    - src/util/system.cpp top (lines 1-25) shows no `#include <config/bitcoin-config.h>` directive (only `#include <util/system.h>` and unrelated headers).
    - The file uses config tokens: `HAVE_MALLOPT_ARENA_MAX` at line 60 and line 1418.
    - The config header is currently pulled in transitively via `src/util/system.h:15` which includes `<config/bitcoin-config.h>`.

  Impact (soft, non-blocking per the agent (restored to blocking by policy)): build is currently correct because of the transitive include path through util/system.h, so this is not a compile or runtime issue today. However, bitcoin#29404's explicit purpose was to make every consumer of HAVE_* tokens independent of header-include order so that future cleanups (removing the include from headers) cannot silently break .cpp files. Leaving src/util/system.cpp without a direct include defeats that invariant for this file specifically and will become an active bug if/when a later backport removes the include from util/system.h.

  Upstream PRs in the dependency chain:
    - bitcoin#28076 (renamed util/system.{h,cpp} -> common/system.{h,cpp}) — not yet backported in Dash. Without it, the scripted-diff in #29404 misses the file at its current Dash path.

  Recommended adaptation (not applied in this read-only review): add the standard guarded include at the top of src/util/system.cpp matching the pattern used elsewhere in this PR:
      #if defined(HAVE_CONFIG_H)
      #include <config/bitcoin-config.h>
      #endif

  Flagging as `suggestion` per the soft-prereq rubric: cherry-pick functions correctly today, but the upstream prerequisite (#28076) is absent and the adaptation needed to keep #29404's invariant on the Dash path was not made.

  ---
  **Policy gate (backport-prereq-restore):** For full upstream backport PRs, a missing prerequisite is blocking unless the finding is explicitly allowlisted (e.g. `intentional_exclusion: true` or a matching entry in `policy_overrides`). The agent's original evidence above is the basis for this block; either backport the prerequisite or annotate the intentional exclusion in the PR description.
- [BLOCKING] src/util/system.cpp:7: Missing adaptation: bitcoin#29404 direct config include
  Carried-forward prior finding: STILL VALID at 19b26e41. Upstream bitcoin#29404 merge 45b2a91897 adds `#if defined(HAVE_CONFIG_H)` / `#include <config/bitcoin-config.h>` to `src/common/system.cpp` before including `common/system.h`. That upstream path is the result of bitcoin#28076's rename of `src/util/system.cpp` to `src/common/system.cpp` (commit 7d3b35004b inside merge 6342348072). Dash has not backported that rename, so the adapted target is still `src/util/system.cpp`. Current head still goes directly from the license header to `#include <util/system.h>` with no direct config include, while the file uses config-derived macros such as `HAVE_MALLOPT_ARENA_MAX`, `HAVE_FDATASYNC`, `HAVE_POSIX_FALLOCATE`, and `HAVE_SYSTEM`. This misses the upstream #29404 prerequisite/adaptation; the fix is to add the same guarded config include at the top of Dash's `src/util/system.cpp`.

  ---
  **Policy gate (backport-prereq-restore):** For full upstream backport PRs, a missing prerequisite is blocking unless the finding is explicitly allowlisted (e.g. `intentional_exclusion: true` or a matching entry in `policy_overrides`). The agent's original evidence above is the basis for this block; either backport the prerequisite or annotate the intentional exclusion in the PR description.

In `src/qt/addressbookpage.cpp`:
- [SUGGESTION] src/qt/addressbookpage.cpp:1-7: Restore direct bitcoin-config.h include — Dash addressbookpage.cpp uses USE_QRCODE (upstream does not)
  This PR's scripted-diff removed the direct `#include <config/bitcoin-config.h>` from src/qt/addressbookpage.cpp to mirror upstream bitcoin#29404. The removal is correct for upstream because Bitcoin Core's addressbookpage.cpp does not reference any bitcoin-config.h token. Dash's copy of this file diverges: it uses `USE_QRCODE` at lines 71, 107, 258, and 266, and `USE_QRCODE` is defined via `AC_DEFINE([USE_QRCODE], [1], …)` in configure.ac:1899, so it lives in bitcoin-config.h.

  After this PR, the file compiles only because of unrelated transitive includes through other qt/ headers. That contradicts the explicit invariant #29404 establishes — every translation unit using a bitcoin-config.h token must include the header directly — and will silently disable the QR address-book actions in QR-enabled Qt builds if a later header cleanup ever removes the transitive path. Add the direct guarded include back at the top of the file (the same pattern used in src/qt/bitcoingui.cpp, src/qt/guiutil.cpp, etc., in this same backport).

These findings are from an automated code review. Verify each finding against the current code and only fix it if needed.

In `src/util/system.cpp`:
- [BLOCKING] src/util/system.cpp:1-7: Carried-forward (STILL VALID): bitcoin#29404 adaptation missing — src/util/system.cpp lacks direct config include
  Verified at HEAD 318d851f: src/util/system.cpp goes straight from the license header (line 5) to `#include <util/system.h>` (line 7) with no direct `#include <config/bitcoin-config.h>`. The file consumes HAVE_MALLOPT_ARENA_MAX (lines 60, 1418), HAVE_FDATASYNC (line 1233), HAVE_POSIX_FALLOCATE (line 1319), and HAVE_SYSTEM (line 1364) — all defined in bitcoin-config.h.

  Upstream bitcoin#29404's scripted-diff added the guarded direct include to every translation unit that uses a HAVE_* token. Upstream's path is `src/common/system.cpp`, renamed from `src/util/system.cpp` by bitcoin#28076 which Dash has not backported, so the scripted-diff invocation missed Dash's still-unrenamed path. The file builds today only via transitive inclusion through util/system.h — exactly the brittle dependency that #29404 is intended to eliminate. If a future header cleanup removes the transitive path, the HAVE_* tokens silently fall through to disabled #else branches (no fdatasync, no posix_fallocate, no mallopt tuning) with no compile error.

  This is a missing prerequisite/adaptation for the full bitcoin#29404 backport. Either backport bitcoin#28076's util→common rename, or add the guarded direct include at the top of src/util/system.cpp as a Dash-side adaptation. (Consolidates prior findings #1, #2, #3.)
- [BLOCKING] src/util/system.cpp:1-25: Carried-forward (STILL VALID): src/util/system.cpp missing direct config include (bitcoin#29404 soft prereq via unbackported bitcoin#28076)
  STATUS at HEAD 318d851f: STILL VALID. Re-read of src/util/system.cpp:1-30 confirms the file still goes from the license header straight to `#include <util/system.h>` (line 7) with no direct `#include <config/bitcoin-config.h>`. The file uses config tokens HAVE_MALLOPT_ARENA_MAX (lines 60, 1418), HAVE_FDATASYNC (line 1233), HAVE_POSIX_FALLOCATE (line 1319), and HAVE_SYSTEM (line 1364).

  Upstream bitcoin#29404's scripted-diff added the guarded direct include to every .cpp/.h consuming HAVE_* tokens. Upstream's path is src/common/system.cpp (renamed by bitcoin#28076); Dash hasn't backported bitcoin#28076, so the scripted-diff invocation in this PR missed Dash's still-unrenamed src/util/system.cpp. Today the build is correct only through the transitive include via src/util/system.h, which is exactly the brittle pattern #29404 was meant to eliminate.

  Missing prerequisite upstream PR: bitcoin#28076 (util/system.{h,cpp} -> common/system.{h,cpp} rename). Without it, the #29404 invariant is not honored on the Dash file layout for this translation unit.

  Fix: add the standard guarded include immediately after the license header, matching the pattern used elsewhere in this PR.

  ---
  **Policy gate (backport-prereq-restore):** For full upstream backport PRs, a missing prerequisite is blocking unless the finding is explicitly allowlisted (e.g. `intentional_exclusion: true` or a matching entry in `policy_overrides`). The agent's original evidence above is the basis for this block; either backport the prerequisite or annotate the intentional exclusion in the PR description.
- [BLOCKING] src/util/system.cpp:7: Carried-forward (STILL VALID): missing adaptation of bitcoin#29404 direct config include
  STATUS at HEAD 318d851f: STILL VALID. Upstream bitcoin#29404 merge 45b2a91897 added `#if defined(HAVE_CONFIG_H)` / `#include <config/bitcoin-config.h>` to src/common/system.cpp before including common/system.h. That upstream path is the product of bitcoin#28076's rename of src/util/system.cpp to src/common/system.cpp (commit 7d3b35004b inside merge 6342348072). Dash has not backported bitcoin#28076, so the adapted target is still src/util/system.cpp. Current head still goes directly from the license header to `#include <util/system.h>` (line 7) with no direct config include, while the file uses HAVE_MALLOPT_ARENA_MAX, HAVE_FDATASYNC, HAVE_POSIX_FALLOCATE, and HAVE_SYSTEM. The #29404 adaptation for the Dash path is still missing.

  Fix: add the same guarded config include block at the top of Dash's src/util/system.cpp.

  ---
  **Policy gate (backport-prereq-restore):** For full upstream backport PRs, a missing prerequisite is blocking unless the finding is explicitly allowlisted (e.g. `intentional_exclusion: true` or a matching entry in `policy_overrides`). The agent's original evidence above is the basis for this block; either backport the prerequisite or annotate the intentional exclusion in the PR description.
- [BLOCKING] src/util/system.cpp:7: Missing prerequisite: bitcoin#28076 leaves bitcoin#29404 hunk unapplied
  Carried-forward prior findings 1, 2, and 3 are STILL VALID at 318d851f. Upstream bitcoin#29404 merge 45b2a91897 adds the guarded `#include <config/bitcoin-config.h>` to `src/common/system.cpp` before including `common/system.h`. Dash still has this translation unit at `src/util/system.cpp`; `git ls-tree` at current head shows `src/util/system.cpp` and no `src/common/system.cpp`. The upstream path mismatch comes from the unbackported upstream move `7d3b35004b refactor: Move system from util to common library` in the dependency chain before #29404. Current Dash `src/util/system.cpp` still goes directly from the license header to `#include <util/system.h>` at line 7, while the same file uses config-derived macros `HAVE_MALLOPT_ARENA_MAX`, `HAVE_FDATASYNC`, `HAVE_POSIX_FALLOCATE`, and `HAVE_SYSTEM`. It currently builds through a transitive include from `util/system.h`, but that is exactly the dependency #29404 is eliminating. Add the guarded config include directly to Dash's still-unrenamed file.

  ---
  **Policy gate (backport-prereq-restore):** For full upstream backport PRs, a missing prerequisite is blocking unless the finding is explicitly allowlisted (e.g. `intentional_exclusion: true` or a matching entry in `policy_overrides`). The agent's original evidence above is the basis for this block; either backport the prerequisite or annotate the intentional exclusion in the PR description.

In `src/qt/addressbookpage.cpp`:
- [BLOCKING] src/qt/addressbookpage.cpp:6-14: Missing adaptation: bitcoin#29404 removed a config include Dash still needs
  Carried-forward prior finding 4 is STILL VALID at 318d851f. Upstream bitcoin#29404 removes `#include <config/bitcoin-config.h>` from `src/qt/addressbookpage.cpp` because upstream's file no longer references config tokens. The Dash backport mirrored that removal, but Dash's `src/qt/addressbookpage.cpp` still uses `USE_QRCODE` at lines 71, 107, 258, and 266; Dash defines `USE_QRCODE` through `configure.ac`, so it is provided by `bitcoin-config.h`. The current file starts with `#include <qt/addressbookpage.h>` at line 6 and has no direct config include. This is a Dash-side adaptation gap in the #29404 invariant: the file now relies on unrelated transitive includes for a config macro.

  ---
  **Policy gate (backport-prereq-restore):** For full upstream backport PRs, a missing prerequisite is blocking unless the finding is explicitly allowlisted (e.g. `intentional_exclusion: true` or a matching entry in `policy_overrides`). The agent's original evidence above is the basis for this block; either backport the prerequisite or annotate the intentional exclusion in the PR description.